[ci:component:github.com/gardener/machine-controller-manager-provider-azure:v0.17.0->v0.17.1] #1320
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes:
[github.com/gardener/machine-controller-manager:v0.60.0]
✨ New Features
[OPERATOR]When running without a target cluster machine-controller-manager will report a new status fieldaddressesby @maboehm [#1012][OPERATOR]Machine Class now has VirtualCapacity field hat maps to WorkerPool's NodeTemplate VirtualCapacity. by @elankath [#1024]🐛 Bug Fixes
[OPERATOR]Fixed metricmcm_machine_set_failed_machinesand underlying variable*machineSet.Status.FailedMachinesso that they reflect the current state of machines by @gagan16k [#1025][USER]Fixed checking ofcreateMachineTimeoutwhen machine isPendingby @thiyyakat [#1015][OPERATOR]Fixed a bug where machines in theInPlaceUpdatingphase were incorrectly transferred to the new machine set during inplace updates. This caused the machine controller to miss updating the phase toInPlaceUpdateSuccessful, resulting in machines getting stuck or marked asInPlaceUpdateFailed. by @acumino [#1020]🏃 Others
[OPERATOR]node.gardener.cloud/critical-components-not-readytaint is added to the node after the successful in-place update to prevent scheduling any workload before critical component pods are ready. by @acumino [#1017][OPERATOR]export testresults as inlined ocm-resource by @heldkat [#1022][DEVELOPER]migrate CICD-Pipeline to GitHub-Actions by @ccwienk [#1011][OPERATOR]Add informational logging for MachineDeployment rollout events by @gagan16k [#1029][DEVELOPER]Convert.reuse/dep5toREUSE.toml. by @thiyyakat [#1026][github.com/gardener/machine-controller-manager:v0.60.1]
🐛 Bug Fixes
[OPERATOR]Added a safeguard to delay deletion of machines that are undergoing aCreateRequest to prevent orphaning of VMs. by @takoverflow [#1045][github.com/gardener/machine-controller-manager-provider-azure:v0.17.1]
🐛 Bug Fixes
[OPERATOR]Fixed an issue in the orphan safety controller where orphaned VM instances were not fully cleaned up in large Azure clusters due to missing pagination in Azure Resource Graph queries. by @gagan16k [#211]🏃 Others
[OPERATOR]Update build workflow to now also build arm64 images by @aaronfern [#211]BoM Diff
Added components: 0
Changed components: 2
Removed components: 0
Changed Components:
⚙ github.com/gardener/machine-controller-manager-provider-azure: v0.17.0 → v0.17.1
⚙ github.com/gardener/machine-controller-manager: v0.60.0 → v0.60.1
Component Details:
⚙ github.com/gardener/machine-controller-manager-provider-azure:v0.17.0 → v0.17.1
⚙ github.com/gardener/machine-controller-manager:v0.60.0 → v0.60.1